home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
doors13.arc
/
MANUAL.ENG
< prev
Wrap
Text File
|
1991-05-22
|
42KB
|
1,387 lines
DOORSWAP
Version 1.30
March/April 1991
by
Volker König
Mettmanner Straße 71
4000 Düsseldorf 1
Germany
FIDO: 2:241/4031.3
DOORSWAP.DOC Version 1.21
April 10, 1991
Table of Contents
1. And another Utility 3
1.1 The Shareware-Concept 4
1.2 License-Agreement 5
1.3 Warranty 7
2. System Requirements 8
2.1 Hardware Requirements 8
2.2 Software Requirements 8
3. Installation 10
3.1 The Swapfile 12
3.2 RAM-Drives 12
3.3 Multiple Swapping 13
4. Options 14
5. A little bit about the Future 16
6. Error Messages 17
7. Index 19
8. Historicals 20
Page 2
DOORSWAP.DOC Version 1.21
April 10, 1991
1. And another Utility
-------------------
What's that, DOORSWAP?
Many BBS-programs offer a function to call software, e.g.
databases, and - or better: mostly - games from within the BBS.
In some BBSes this function is realized not quite useful and
sometimes one must assume it is installed for optical reasons
only.
More and more external programs - just like Omen Software's DSZ -
are used instead of inventing the wheel for a second (third...)
time. At least transfer-protocols are much easier to update and
a BBS can use protocols and compression-routines unknown at
program's day-of-release simply by installing another child-
process.
To use these toolkits there must exist a possibility of calling
external programs from within the BBS - just what the BASIC-
command SHELL or the C-procedure SYSTEM does. Sometimes the DOOR-
or GAME-function seems to be installed basing on this small shell
in order to make the BBS look more professional. Most of the
programs called by such routines fail working just because they
do not get enough memory.
This was exactly the problem we got while installing Tradewars ][
on a BBS running under Forem-PC 2.3. Both worked without
bothering each other - except the crashdowns at every third or
fourth start of Tradewars.
"Why the hell isn't there a way to fool DOS?"
There is one.
After lots of nights with few sleep, after some lost weekends,
after researching in magazines and books (specially at the
Düsseldorf public library and their collection of the german
computer-magazine "c't") DOORSWAP was born.
At this place I would like to say something about my english...
I've learned the english language for nine years at a german
school preparing for university; similar to the american "high
school". Since I finished school about six years ago there might
be some faults and errors in this manual. I would like to quote
God's Final Message to His Creature (as Douglas Adams assumes it
to be in his book 'So long and thanks for all the fish'):
WE APOLOGIZE FOR THE INCONVENIENCE
Page 3
DOORSWAP.DOC Version 1.21
April 10, 1991
1.1 The Shareware-Concept
---------------------
I think there is not much to be told about.
DOORSWAP is a piece of commercial software. It is no 'freeware'
and not in the public domain. You must not use it (except for
evaluation) without having a written license. But there is one
difference between DOORSWAP and software sold in a store for lots
of money: You can copy and share and evaluate it with only few
restrictions. One of these restrictions is that DOOR.EXE, a part
of DOORSWAP, fails to work on every day that can be divided by 5
without modity (IF (DayOfMonth MOD 5) = 0).
Offer DOORSWAP in your BBS or your Software Library, evaluate
it's usability - but if you keep on using it regularly after
evaluating you will have to pay for it.
With this I give the right to copy and share the program DOORSWAP
given in the packet DOORS12.COM to the public domain as long as
- no file or part is added, removed or changed
- it is distributed completely without any additional copyright-
notice as file DOORS121.COM
- it is not distributed in addition with or as part of any other
product (excluding collections of toolkits that can be shared
and copied without restrictions)
- the fee for copying DOORSWAP or the collection containing
DOORSWAP does not extend US$ 3,-- / DM 5,--
Page 4
DOORSWAP.DOC Version 1.21
April 10, 1991
1.2 License-Agreement
-----------------
The german "Urhebergesetz", the law concerned with what is called
copyright in the english language, does not allow any use of
copyrighted materials without the prior consent of the person who
created the materials. Using them without consent can cause
criminal prosecution and can become very expensive. I think there
are laws (like the french "Code Punal") very similar in every
country.
For a fee of US$ 20,-- (cash, by order cheque or bank order) I
will ship your personal copy of DOORSWAP 1.30 including your
personal license-number and your BBS's name. And, of course,
without that ugly "evaluation"-message and the every-fifth-day-
restriction. The US$-20 - fee is the fee for orders outside
germany. For orders from inside germany see the file MANUAL.DEU.
This registered copy must not be copied anymore outside your BBS.
You can use it on as may ports of one BBS. For more than one
BBSes please contact me to get information about a site-license.
It might be cheaper than one single copy for each BBS.
In case you are already registered user of an older version of
DOORSWAP you can get an update to 1.30 for only US$-12,-- .
Since I am interested in enhancing doorswap, changes for your
hardware or customizations to your needs are possible.
Please contact me for registration at the following address
Volker König
Mettmannerstraße 71
W-4000 Düsseldorf 1
Germany
You can pay either by order-cheque or cash. If you want to pay by
bank order I will not ship your registered version before the
money has reached my account.
Page 5
DOORSWAP.DOC Version 1.21
April 10, 1991
At registration please answer the following questions:
At which BBS DOORSWAP
will be used? ________________________________________
Phone-number: _________________ Net? ________________
BBS-Software: ________________________________________
Online-Games(s): ________________________________________
_________________________________________________________________
DOS-Version: ________________________________________
additional software: ________________________________________
Hardware
o PC/XT Memory (+EMS/XMS) _______ kByte
o PC/AT (80286) Available for DOS _______ kByte
o PC/AT (80386/80486) RAM-Drive _______ kByte
o PS/2 Model ______ __ Harddisk(s) with
_________ MByte Memory
Of course these data are confidental. I will not tell anybody
about what your hardware and software is except it is necessary
to solve any problems.
Page 6
DOORSWAP.DOC Version 1.21
April 10, 1991
1.3 Warranty
--------
You can imagine that I don't want to be responsible for any
damages at your hard- and/or software caused by DOORSWAP. To
cover the possible costs of only one crash I would have to sell
the registration of DOORSWAP for much more than US$-20.
There is a warranty of six month stated in the german
"Bürgerliches Gesetzbuch", our civil law. I cannot avoid to
return the money if DOORSWAP does *really* not work but I think
you will have evaluated it before registering and you definitely
know the bugs. I also do not give any warranty except that
DOORSWAP will work on a
AT 286, manufactured by MANDAX (Taiwan), AMI-BIOS, Harddisk
ST225, Hercules-Graphic-Card, MS-DOS 3.20
with FOREM-PC 2.30 and Tradewars ][.
I am only responsible for faults, errors and damages if your
installation fits with mine.
Page 7
DOORSWAP.DOC Version 1.21
April 10, 1991
2 System Requirements
-------------------
DOORSWAP should work properly on every MS-DOS computer having a
harddisk, not using the interrupt 62H for any other dirty
tricks and running with MS-DOS 3.20 or later. I had to take care
of some bugs of DOS 3.20 but they obviously did not change until
DOS 4.01. Who knows what later versions will bring up!
DOORSWAP did not work with GALACTIC WARZONE and FOREM-PC 2.3 on a
Commodore PC-10. Since WARZONE did not run without FOREM and
DOORSWAP just as well it seems to be a fault of this certain
Commodore-BIOS.
2.1 Hardware Requirements
---------------------
There should exist a harddisk "C:" with about 700 kBytes of free
memory.
An advantage - but not required - is a communications-card
(COM-Port, RS232 or "serial Port") using an UART 8250 chip. As
you will realize starting DOOR.EXE this program looks out for
the first COM-Port having a carrier-detect (CD) signal set to
send a small copyright-notice.
Calling DOORSWAP always causes a delay depending in your
harddisk's speed. Not every BBS offers you a possibility to write
out a message like "please wait, DOORSWAP's working" to your COM-
Port. A short message about DOORSWAP and a little bit
merchandising won't insult anybody.
To find out to which COM-Port the modem is connected DOORSWAP
examines up to four ports for CD. The first one found carrying CD
is assumed to be active. If no CD is found no message will be
written to any COM-Port.
From version 1.30 on you can bypass this messages by using an
option (refer to 'options' in this manual) or let DOOR.EXE use an
installed FOSSIL-driver instead.
2.2 Software requirements
---------------------
The use of MS-DOS 3.20 is highly recommended. As I mentioned
before I had to use some DOS-functions that are not yet
documented by Microsoft. Especially the design of the memory
control blocks (MCB) is destined for internal use of DOS itself
and might change in later versions.
But I did beta-tests on several DOS-Versions from 3.00 up to 4.01
Page 8
DOORSWAP.DOC Version 1.21
April 10, 1991
and there were no considerable problems.
RAM-drives and cache-memory must not be installed in DOS-memory,
please use Extended- or Expanded-Memory. Otherwise the whole DOS-
Memory might be swapped out including those areas reserved for
RAM-drive or cache what can easily bring up system crashes.
You can install device drivers (like ANSI.SYS) as before. Please
assure that they do not try to fool DOS just like DOORSWAP does.
It is also necessary to have them installed before DOORSWAP.COM
is loaded. Since DOORSWAP swapps out the whole memory behind the
end of DOORSWAP.COM all TSR-Programs loaded after DOORSWAP.COM
will disappear while the external program works.
But the evaluation-copy is made just for testing where there are
problems caused by other TSR's. Keyboard-drivers and other useful
things like SIDEKICK and it's clones will normally cooperate
without problems.
Just like the BBS-program the externally loaded software must not
try to fool DOS. You should not install any resident software
after the memory has been swapped out because they will be
deleted from RAM loading the memory back.
Problems might come up using FOSSIL-drivers (like X00.SYS or
BNU.SYS) although they did not come up at the beta-test. Normally
DOS manages the entry-points of interrupts itself by writing them
into a special area of RAM. DOORSWAP and DOS can see where and
where not a vector has been changed since installation of
DOORSWAP.COM and restore it to it's previous value. FOSSIL-
drivers can chain new processes into the ticker-interrupt or the
INT 14H (COM-Port) bypassing this convention. More about this
problem in a later part.
A RAM-drive can be installed in either Extended- or Expanded
memory. If it is so you can keep on using it. A RAM-drive or a
cache-program using DOS-memory can not be used.
Page 9
DOORSWAP.DOC Version 1.21
April 10, 1991
3. Installation
------------
There is not to say much about installing DOORSWAP. As you will
already have realized DOORSWAP consists of two separate programs:
DOORSWAP.COM and DOOR.EXE. DOORSWAP.COM is the resident portion.
Installed it saves the current interrupt vectors and moves one of
them to it's own entry-point.
DOOR.EXE is the activating part. As parameter it needs the
previous commandline used to call the external program. DOOR.EXE
finds out which COM-Port is used, and what COMSPEC and DSFILE are
set to. After that DOORSWAP.EXE is activated by calling it's
interrupt and passing some data.
Those data are
- name and path of the commandline interpreter (defaults to
C:\COMMAND.COM
- parameter for calling the interpreter ("/C " plus the
commandline)
- name and path of the swap-file defined in DSFILE (defaults to
C:\DOORSWAP.DAT)
I assume most BBS-programs are installed inside a BATCH-loop
that is called by AUTOEXEC.BAT. If this is your installation I
would propose to call DOORSWAP.COM as the last program before
entering the BBS-batch from AUTOEXEC.BAT.
If your BBS is running in a loop inside AUTOEXEC.BAT DOORSWAP.COM
should be called as the last program before entering the loop.
NOTE: Multiple installations are still possible with version 1.3.
The single installations of DOORSWAP.COM will not bother each
other but they will waste about 6 kBytes of memory for each of
them.
From inside the BBS there are different ways to install the
activating program DOOR.EXE in the most efficient way.
In the majority of cases external programs will be called as a
shell-function. The BBS-program is told how you would call the
external program from DOS. Assuming the external program is
named GAME.EXE and needs the number of the COM-port or the word
LOCAL passed as parameter it would be called from DOS:
GAME COM1
Page 10
DOORSWAP.DOC Version 1.21
April 10, 1991
This is exactly what you have to tell the BBS to call GAME.EXE.
Calling it via DOORSWAP change it to
DOOR GAME COM1
/^^^^^^^^^
(former commandline)
You just have to call DOOR.EXE passing the former commandline as
parameter string. This very simple installation is possible e.g.
at FOREM PC or SearchLight BBS and many other programs. You do
not need to change anything but the commandline.
Some very simple implementations of door functions use the first
word of the commandline as the BBS-command the user has to enter
in order to start the external program. In the case previously
described the commandline
GAME COM1
would mean the program would have to be called with the BBS-command
GAME (the 1st word of the commandline executed). Since normally
the names of the programs called from within the BBS are
different there will be no problems with it - unless you use
DOORSWAP. Now DOOR will be the very first word of more than one
commandline and this will cause either an error-message or that
only one of the programs installed can be called by the user.
You can avoid problems by creating BATCH-files do call the
different programs. Within this BATCH-file you call the
external program using the former new commandline. In our
example the BATCH-file could be named GAME.BAT and be placed in
the DOS-directory or the BBS-directory. It should contain:
CD C:\GAME1
DOOR GAME COM1
CD C:\BBS
You can further write out messages to your COM-Port with the
COPY-command or use the CLS-command to clear the local screen.
NOTE:
-----
After installing DOORSWAP.COM there must be at least one program
installed or loaded. Calling DOOR.EXE from the same COMMAND-Shell
where DOORSWAP was installed is nonsense because DOORSWAP will
not be able to free more memory than available at that moment
anyway, and will end up in a system crash.
Page 11
DOORSWAP.DOC Version 1.21
April 10, 1991
3.1 The Swapfile
------------
From version 1.20 you will have the option to change the swapfile's
name. The new name you choose should be fully qualified, that
means it should consist of drive, path (starting with '\') and
filename. The name is set using the environment variable DSFILE.
Use the command
SET DSFILE=xxx
to set DSFILE. If DSFILE is not set the filename C:\DOORSWAP.DAT
is used.
The name should be fully qualified. If there are parts missing
the current settings (current drive and/or path) will be used. In
case the program called changes either path or drive the swapfile
will not be found to reload the memory. A system crash cannot be
avoided in this case, so use qualified names.
The following errors are possible:
C:DOORSWAP.DAT
The file DOORSWAP.DAT will be placed in the current path of drive
C:. If another path and/or drive is set after exiting the
external program reloading memory is impossible.
\BBS\DOORSWAP.DAT
The file will be located in the path \BBS\ of the current drive.
If the drive is changed after execution of the external program
there is a real problem ;-)
TEMP\DOORSWAP.DAT
The path .\TEMP\ is used to place the swapfile in. Since "." is a
synonym for the current path DOORSWAP.DAT will be placed in the
sub-directory TEMP of the current path. If the external program
changes current path and/or drive the reloading might cause
problems.
3.2 RAM-Drives
----------
You can use the option described to use a RAM-drive as a
swapping-drive. You must be sure that there is enough memory on
this RAM-dive to hold the swapfile that can grow up to about 600
kBytes. The swapping will become terribly fast.
Page 12
DOORSWAP.DOC Version 1.21
April 10, 1991
3.3 Multiple Swapping
-----------------
The possibility of customizing the name of the swapfile can be
used for some tricks.
If the called program itself can call external programs but does
not free enough memory you can install DOORSWAP.COM for a second
time and swap out the memory into a second swapfile. A sample
installation in a very, very short form:
The BBS used is named BBS.EXE. There exist two different
installations, one in path INST_1 and one in INST_2. Maybe you
want to call installation 2 from installation 1 because you are
participating in two different networks.
The BATCH-file calling the *first* BBS should contain the
following lines:
[...]
CD \INST_1
SET DSFILE=C:\BBS\DOORSWAP.001
BBS
[...]
The BATCH-file calling the *second* installation should contain
the following lines:
[...]
DOORSWAP
CD \INST_2
SET DSFILE=C:\BBS\DOORSWAP.002
BBS
[...]
Look at the names DSFILE is set to and the second installation of
DOORSWAP.COM.
Page 13
DOORSWAP.DOC Version 1.21
April 10, 1991
4. Options
-------
From version 1.30 some options are available to customize
DOORSWAP to your needs. They are enabled or disabled by setting
the environment variable DSOPT to a string containing several
keywords seperated by commas. An example for such a definition
would be:
SET DSOPT=DEL;FOSOUT;FOSINIT
Now the options in particular:
DEL - delete swap-file after use
Using this option causes DOOR.EXE to delete the swap-file after
loading back memory. You can use this if the memory on your
harddisk used by the swap-file is needed for other things,
importing messages from or exporting them to a network like
FidoNet.
COMx - tell DOOR.EXE which COM-port is to be used
This option causes DOOR.EXE to make use of the COM-Port defined
instead of the 'x'. If your BBS does have more than one ports the
search for the first carrier-detect can cause the messages to be
sent to the wrong BBS. Also a non-standard-UART can cause
problems. You can also use COM0 to suppress the use of any COM-
port.
FOSOUT - use FOSSIL-driver to write messages to COM-port
You can force DOORSWAP to use the FOSSIL-driver you have possibly
installed to write the messages to the COM-port. I can only
propose the use of a FOSSIL-driver to avoid complications by
'unauthorized' use of the port.
FOSINIT - initialize FOSSIL-driver after loading
Some online games do not manage to return the COM-port to the BBS
in the status they found it. There could interrupt-masks be
abused, interrupt-vectors (also of FOSSIL) dismanaged and so on.
You can assume this to have happened if the BBS does not accept
any input at least via COM-port after returning.
This is originally no problem caused by DOORSWAP, but DOORSWAP
can help solving it. In case your BBS makes use of a FOSSIL-
driver you can re-initialize this driver to the port used after
Page 14
DOORSWAP.DOC Version 1.21
April 10, 1991
loading the memory. In some (not all) cases it will solve
problems.
And here a further example for the use of multiple options:
since your harddisk is slow you want DOORSWAP to write it's
message to COM2 in order to make the user aware of why it takes
such a long time. COM2 is recommended to be used since you are
driving two ports within a multitasking-environment.
Each morning you are polling from your boss the free space on
your harddisk becomes rare. So you want DOORSWAP to delete its
swap-file after loading back the memory. In addition you want
your FOSSIL-driver (X00.SYS) to be initialized since THE PIT does
not return the port properly. Also FOSSIL should be used to write
the messages to avoid any trouble that can be avoided.
To reach this you have to set DSOPT somewhere - possible in
AUTOEXEC.BAT by the following commandline:
SET DSOPT=COM2;DEL;FOSINIT;FOSOUT
Page 15
DOORSWAP.DOC Version 1.21
April 10, 1991
5. A little bit about the future
-----------------------------
Yes, DOORSWAP shall be enhanced in later versions.
If there grow up problems on different systems than the ones I
have tested, DOORSWAP will be changed to work on these systems,
too. But for this I need your support. If you find any problems -
contact me. Of course you can also contact me before registering
since I am of the opinion that the evaluation of a shareware-
program is the only way to find bugs.
Let me tell some word about things I intend to change in future
versions.
It is planned to let you select the interrupt-vector used to
activate DOORSWAP. Perhaps some software uses int 62H itself and
might conflict with DOORSWAP.
And some day I will think about a way to avoid wrong multiple
installations of DOORSWAP.COM.
Page 16
DOORSWAP.DOC Version 1.21
April 10, 1991
6 Error Messages
--------------
Some easy-to-understand messages could be caused by the runtime-
library of Fitted Software Tools' Modula-2 compiler. DOOR.EXE is
written completely in M2. There is not much to do about them.
DOORSWAP.COM can write out error messages while swapping, too.
They are - as I think - self-declaratory and do not say anything
important. In fact they only tell something about a missed try to
fool DOS. If DOORSWAP works correctly and the error message is
sent it is just caused by an unexpected response of any DOS-
function. In this case you won't be able to change it unless you
send me a copy of your DOS - please DON'T do so. If DOORSWAP
works this message won't bother anybody.
The only messages interesting for DOORSWAP-users are the ones
written out while loading COMMAND.COM.
In former versions I have been to lazy to let DOORSWAP.COM or
DOOR.EXE write out those messages returned from DOS by a numeric
code. To make it easy I just added 0x20 (chr$(32)) to make the
DOS-response-code visible as an ASCII-char.
From version 1.21 DOOR.EXE will analyze the code after returning
from interrupt-action. All these messages are concerned with
COMMAND.COM or whatever commandline-interpreter you are using.
6.1 'returned from DOORSWAP without Error.'
Lucky guy, it works!
6.2 'FATAL ERROR: Illegal call of DOS-Function.'
It seems to be a very fatal error: the DOS-function used to start
a child-process cannot make sense of the parameters passed to it
by DOORSWAP. Check whether or not there are unauthorized changes
in either DOOR.EXE or DOORSWAP.COM. If not: Possibly you are
using a DOS older than 3.0 ?
6.3 "COMSPEC 'C:\COMMAND.COM' not found!"
The file 'C:\COMMAND.COM' (or whatever is defined in COMSPEC) is
not found. Please check this.
6.4 "Out of memory error: can't load 'C:\COMMAND.COM'!"
This should really not happen, because DOORSWAP first swaps out
memory and frees it for DOS and then loads COMMAND.COM. Possibly
the memory-management of your DOS-version differs from what was
'normal' at DOS 3.xx.
Page 17
DOORSWAP.DOC Version 1.21
April 10, 1991
6.5 "ERROR in file 'C:\COMMAND.COM' - maybe bad EXE"
Your COMSPEC-File is an EXE-File having a damaged header. Replace
it by a copy from your DOS-Mastercopy (if you have one)
6.6 'Unknown Error.'
DOS returns an error-code unknown at versions up to DOS 4.01.
Use an older DOS-Version.
Page 18
DOORSWAP.DOC Version 1.21
April 10, 1991
7. Index
-----
activating program 10 MS-DOS 8
Address 5 multiple installation 10
ANSI.SYS 9
AUTOEXEC.BAT 10 options 8
Bank order 5 parameter 10
BAT 10 price 4
batch 10
BNU.SYS 9 RAM-drive 9
Registration fee 4,5
Cache memory 9 resident part 10
carrier-detect 8 RS232 8
COM port 8
COMMAND.COM 10 serial port 8
Commodore PC 10 8 Shareware 4
compression 3 SHELL 3
COMSPEC 10 SideKick 9
Software Library 4
databases 3 software requirements 8
device drivers 9 SYSTEM 3
disk space 8 System requirements 8
DOOR-function 3
DOOR.EXE 10 ticker-interrupt 9
DOORSWAP.COM 10 Tradewars ][ 3
DSFILE 10 transfer-protocols 3
DSZ 3 TSR 9
environment 10 UART 8250 8
extended memory 9
external programs 3 Warranty 7
FoReM PC 3 X00.sys 9
FOSSIL 8,9
GALACTIC WARZONE 8
GAME-function 3
God 3
harddisk 8
installation 10
INT 62h 8
keyboard-drivers 9
License Agreement 5
Page 19
DOORSWAP.DOC Version 1.21
April 10, 1991
8. Historicals
-----------
And here some small sentences about DOORSWAP's history.
03.08.1990 1st release of DOORSWAP 1.0. Also date of the
authorized package DOORS10.COM
03.11.1990 Start of work at DOORSWAP 1.1.
Especially some bad manners of TurboPascal
3.00's runtime-library had to be changed. TP3.0
normally uses own screen-output based on the INT
10H of the BIOS. At startup it tries to force
the display into a defined mode. That was a
problem at some 'compatible' BIOSses and
graphic-cards.
It was fooled by changing the output to STDOUT.
V1.1 of DOORSWAP was not published as shareware
but used to register from May '90 on.
11.22.1990 Release of DOORSWAP 1.2. There are the following
changes:
- DOOR.EXE, former DOOR.COM, is coded in
Modula-2 instead of Pascal. Since I own the
library-sources of this compiler I definitely
know there won't be problems with your BIOS.
- DOOR.EXE now detects the presence of
DOORSWAP.COM V1.2.
- DOOR.EXE evaluates the environment-variable
DSFILE to determine the swapfile's name.
28.02.1991 Release of DOORSWAP 1.21. I made some small
optical changes and a bugfix.
There were indeed problems with some COM-ports.
They were not found by DqOOR.EXE and so on some
systems a random-address found somwhere in DOS-
memory was assumed to be the active COM-Port. On
other systems with less than four ports the
value of 0H of not existing COM-ports in the
DOS-table was assumed to be Ok. At 0H there is
the DMA-controller which looks not unlike an
avtive COM-port. So the message was written to
the DMA-controller - causing strange meditation-
sessions of the system. Since I couldn't
reproduce these errors on my system I coudn't
avoid them. Sorry for this.
05.04.1991 Beta tests of V 1.30 are done. slowly the
release of V 1.30 comes closer.
The following changes have been made:
Page 20
DOORSWAP.DOC Version 1.21
April 10, 1991
- evaluation-copy does not work each day.
- now you can suppress the messages.
- FOSSILs can be used for output.
- FOSSILs can be re-initialized
- DOOR.EXE can delete the swap-file
- the messages are made a bit more beautiful.
Some BBSes do not write CR's past the input of a
command. So the messages sometimes were written
into the same line the command was entered.
- the documentation contains an alphabetical
index.
Page 21